Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1182

reference: 124-tree-1
name: 1182
tree-preservation-order: undefined
124-tpo-1
uprn
address-text
point: POINT (-1.030099 50.866568)
geometry: MULTIPOLYGON (((-1.030028 50.866561,-1.030031 50.866575,-1.030041 50.866587,-1.030056 50.866597,-1.030076 50.866604,-1.030098 50.866606,-1.030120 50.866604,-1.030140 50.866598,-1.030156 50.866588,-1.030166 50.866576,-1.030170 50.866562,-1.030167 50.866548,-1.030157 50.866535,-1.030142 50.866525,-1.030122 50.866519,-1.030100 50.866516,-1.030078 50.866518,-1.030058 50.866524,-1.030042 50.866534,-1.030032 50.866547,-1.030028 50.866561)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL